Querying data from devices in an ad-hoc network

ABSTRACT

A mobile data network supports making subscriber data addressable as devices in a mobile data network. Each data chunk is assigned a device address in the mobile data network. The data chunk can then be addressed as a device in the mobile data network. Data chunks corresponding to a subscriber are distributed across multiple devices in the mobile data network, which may include subscriber devices, network components in the mobile data network, and specialized devices provided by storage providers. The mobile data network is queried to determine related devices. An ad-hoc network of the related devices is formed. A data query by one of the related devices is sent to the related devices in the ad-hoc network to determine whether the data query can be satisfied by one of the related devices. If not, the data query is sent via normal channels in the mobile data network.

BACKGROUND

1. Technical Field

This disclosure generally relates to mobile data networks, and more specifically relates to querying data from related devices in an ad-hoc network.

2. Background Art

Mobile phones have evolved into “smart phones” that allow a subscriber not only to make a call, but also to access data, such as e-mails, the internet, etc. Mobile phone networks have evolved as well to provide the data services that new mobile devices require. For example, 3G and 4G networks cover most of the United States, and allow subscribers high-speed wireless data access on their mobile devices. In addition, phones are not the only devices that can access mobile data networks. Many mobile phone companies provide equipment and services that allow a subscriber to plug a mobile access card into a Universal Serial Bus (USB) port on a laptop computer, and provide wireless internet to the laptop computer through the mobile data network. In addition, some newer mobile phones allow the mobile phone to function as a wireless hotspot, which supports connecting several laptop computers or other wireless devices to the mobile phone, which in turn provides data services via the mobile data network. As time marches on, the amount of data served on mobile data networks will continue to rise exponentially.

Most data transfers in a mobile data network are initiated by a subscriber. One way for a subscriber to initiate a data transfer is to send an e-mail, or to invoke a web page. There have been some attempts at making data transfers across mobile devices data-centric. One form of data-centric communication uses a publish-subscribe model, which allows subscribers to sign up for data. When a data source publishes data, the data is sent to all subscribers who have signed up for the data. The advantage of this type of data-centric communication is the data can be exchanged without the publisher knowing anything about the subscribers (other than where to deliver the data) and without the subscribers knowing anything about the publisher (other than how to sign up for the data). Instead both publishers and subscribers focus on what the data is as inscribed in the definition of the data.

Internet-based services have arisen that allow a user to store a large amount of the user's data in the cloud. Cloud-based services take advantage of storage and processing capacity that is both readily available and easily expandable in the cloud. While these Internet-based services can be used by subscribers of a mobile data network, these services are cloud-based and are not provided within a mobile data network. Thus, the problem of storing subscriber data in a mobile data network remains largely unsolved. Data-centric communication in mobile data networks has not caught on due to the lack of known mapping between subscribers and data, due to a lack of scalable storage capability across the mobile data network, and due to the lack of service with continuous infrastructure connectivity. While known mobile data networks can be used as a conduit for accessing cloud-based storage for subscribers, known mobile data networks do not offer support for storing subscriber data in the mobile data network.

BRIEF SUMMARY

A mobile data network supports making subscriber data addressable as devices in a mobile data network. Each data chunk is assigned a device address in the mobile data network. The data chunk can then be addressed as a device in the mobile data network. Data chunks corresponding to a subscriber are distributed across multiple devices in the mobile data network, which may include subscriber devices, network components in the mobile data network, and specialized devices provided by storage providers. The mobile data network is queried to determine related devices. An ad-hoc network of the related devices is formed. A data query by one of the related devices is sent to the related devices in the ad-hoc network to determine whether the data query can be satisfied by one of the related devices. If not, the data query is sent via normal channels in the mobile data network.

The foregoing and other features and advantages will be apparent from the following more particular description, as illustrated in the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

The disclosure will be described in conjunction with the appended drawings, where like designations denote like elements, and:

FIG. 1 is a block diagram of a data chunk that is addressable as a device in a mobile data network;

FIG. 2 is a flow diagram of a method for making a data chunk addressable as a device in a mobile data network;

FIG. 3 is a block diagram showing a prior art mobile data network;

FIG. 4 is a diagram showing information that is included in prior art Home Location Register (HLR) entries;

FIG. 5 is a diagram showing configuration for a known MSISDN;

FIG. 6 is a diagram showing how a known MSISDN can have multiple sub-addresses;

FIG. 7 is a flow diagram of a method for making a data chunk addressable as a device in a known mobile data network;

FIG. 8 is a flow diagram of a method for receiving data from a data chunk that is addressable as a device in a mobile data network;

FIG. 9 is a block diagram of a method for receiving data from a data chunk that is addressable as a device in a prior art mobile data network;

FIG. 10 is a block diagram of a mobile data network that includes a subscriber data mechanism that tracks, transfers and manages subscriber data in a mobile data network that is addressable as a device;

FIG. 11 is a flow diagram of a method for the subscriber data mechanism in FIG. 10 to make a data chunk addressable as a device in the mobile data network;

FIG. 12 is a flow diagram of a method for a device in a mobile data network to request data that is addressable as a device;

FIG. 13 is a diagram that shows examples of data that could be stored in the data chunk status field in FIG. 1;

FIG. 14 is a table showing one suitable way for the subscriber data tracking mechanism in FIG. 10 to keep track of subscriber data in a mobile data network;

FIG. 15 is a block diagram showing subscriber data stored across multiple mobile devices;

FIG. 16 is a block diagram showing how subscriber data may be parsed into different data chunks that are distributed among different devices in a mobile data network;

FIG. 17 is a table showing different file types for subscriber data that could be parsed into multiple data chunks;

FIG. 18 is a flow diagram of a method for distributing subscriber data in a mobile data network;

FIG. 19 is a block diagram showing a subscriber's data can be stored on many different types of devices that may access the mobile data network;

FIG. 20 is a block diagram of a first embodiment of a subscriber data app;

FIG. 21 is a flow diagram of a method for logging historical data use by a subscriber;

FIG. 22 is a flow diagram of a method for using the logged historical data use by a subscriber to predictively move the subscriber's data;

FIG. 23 is a flow diagram of a method that allows a subscriber to pay a fee to have the subscriber's data stored in a better location;

FIG. 24 is a block diagram showing multiple subscriber devices connected to each other in an ad-hoc network;

FIG. 25 is a block diagram of a second embodiment of a subscriber data app;

FIG. 26 is a flow diagram of a method for establishing an ad-hoc network of related devices;

FIG. 27 is a block diagram showing embodiments of relation criteria;

FIG. 28 is a flow diagram for processing a data query for a device connected to other devices in an ad-hoc network; and

FIG. 29 is a flow diagram of a method for creating an ad-hoc grouping of basestations to satisfy similar queries.

DETAILED DESCRIPTION

As discussed above in the Background of the Invention section, while known mobile data networks can be used as a conduit for accessing cloud-based storage for subscribers, known mobile data networks do not offer support for storing subscriber data in the mobile data network. The mobile data network disclosed and claimed herein allows storing subscriber data in a mobile data network distributed across multiple devices and device types in the mobile data network.

A mobile data network supports making subscriber data addressable as devices in a mobile data network. Each data chunk is assigned a device address in the mobile data network. The data chunk can then be addressed as a device in the mobile data network. Data chunks corresponding to a subscriber are distributed across multiple devices in the mobile data network, which may include subscriber devices, network components in the mobile data network, and specialized devices provided by storage providers. The mobile data network is queried to determine related devices. An ad-hoc network of the related devices is formed. A data query by one of the related devices is sent to the related devices in the ad-hoc network to determine whether the data query can be satisfied by one of the related devices. If not, the data query is sent via normal channels in the mobile data network.

Referring to FIG. 1, a data chunk 110 represents any data that could exist in a mobile data network. Data chunk 110 is a data structure and includes no hardware. In one particular case, data chunk 110 represents data corresponding to a subscriber of the mobile data network. The data chunk 110 includes a device address 120 that makes the data chunk addressable as a device in the mobile data network. The data chunk may additionally include a status 130 that may include one or more pieces of information related to the status of the data chunk, as discussed in more detail below with reference to FIG. 13. Data chunk 110 also includes a communication mechanism 140. The communication mechanism 140 includes a communication interface 150 and communication logic 160. The communication interface 150 is used by a device in the mobile data network to request the data stored in the data chunk 110 using the device address 120. The communication logic 160 determines when and how the data chunk 110 delivers its data when a request for the data is received on the communication interface 150. The data portion 170 is subscriber data stored in the data chunk. When a device in the mobile data network needs to access the data portion 170 in data chunk 110, it sends a request to the communication interface 150 by using the device address 120, and in response, the data chunk 110 delivers the data portion 170 via the communication interface 150 according to the communication logic 160.

FIG. 2 shows a method 200 for making a data chunk for a subscriber addressable in a known mobile data network, such as a 3G or 4G network. A device address corresponding to the subscriber is written as the device address of the data chunk (step 210). The device address of the data chunk is then written to the Home Location Register (HLR) entry for the subscriber (step 220). The HLR is well-known in 3G and 4G networks. By strategically using device addresses compatible with existing 3G and 4G networks, and recording the data chunk as a subscriber device in the HLR, a first implementation can use existing infrastructure in an existing 3G or 4G mobile data network to make the data chunk addressable as a device so the data can be retrieved when needed by a device in the mobile data network.

A prior art mobile data network 300 is shown in FIG. 3. User equipment 310, such as a smart phone, communicates with a tower 320, which communicates with a basestation 330. User equipment 310 can include any suitable device capable of communicating with tower 320. The basestation 330 is coupled to one or more components in the mobile data network. For the sake of illustration and simplicity, the portion of the network that communicates with the basestation 330 is shown in FIG. 3 as network 340, and can include any suitable number and type of components that exist in prior art mobile data networks. The network 340 includes a Home Location Register 350 and a Visitor Location Register 360. The Home Location Register 350 contains information regarding subscribers. The Visitor Location Register 360 contains information retrieved from a subscriber's Home Location Register 350 when the subscriber is outside his or her home network. The function of known Home Location Registers and Visitor Location Registers is well-known in the art, and therefore is not discussed in detail here.

Details of information that is stored in a Home Location Register (HLR) 350 are shown in FIG. 4. An entry 410 in the HLR for a subscriber can include a Subscriber ID, Location, Services, Settings and Other information, as shown in FIG. 4. The Subscriber ID typically includes an International Mobile Subscriber Identity (IMSI) and one or more Mobile Station International Subscriber Directory Number (MSISDNs). The IMSI is typically used as a key in the HLR while the MSISDN is the number normally dialed to connect a call to a mobile phone. An IMSI for a device does not change, while there may be multiple MSISDNs associated with an IMSI.

As shown in FIG. 5, an MSISDN typically includes a Country Code, a National Destination Code, and a Subscriber Number. A feature of known MSISDNs that allows implementing data chunks addressable as devices is that an MSISDN may have a sub-address, as shown in FIG. 6. A sub-address can be up to twenty octets. This allows sub-addresses of an MSISDN to be used to address the subscriber's data chunks. Thus, if a subscriber has a smart phone and also has a tablet computer that both use the same subscription to the mobile data network, the sub-address could be used to differentiate between these two physical devices. By making data addressable as a device, the known methods for storing device information for a subscriber may be used to store information for data chunks for the subscriber.

Referring to FIG. 7, a method 700 is preferably performed to make a data chunk for a subscriber addressable as a device in a mobile data network. The HLR entry for the subscriber is read (step 710). The next unused MSISDN sub-address for the subscriber is determined (step 720). This MSISDN with the next unused sub-address is then written as the device address for the data chunk (step 730). Referring again to FIG. 1, step 730 in FIG. 7 writes the MSISDN with the next unused sub-address to the device address 120 for data chunk 110. The MSISDN with the next unused sub-address that was written to the data chunk is then written to the subscriber's entry in the HLR (step 740). Writing the MSISDN and sub-address to the subscriber's entry in the HLR in step 740 effectively registers the data chunk as belonging to the subscriber, along with the device address needed to access the data chunk. While steps 720, 730 and 740 refer to the next unused MSISDN sub-address for the subscriber, any unused MSISDN sub-address could be used.

FIG. 8 shows a method 800 for retrieving data from a data chunk that is addressable as a device. The data is requested from the data chunk using the device address of the data chunk (step 810). In response, the data chunk sends the data to the requester (step 820). There are numerous ways to implement method 800 in a mobile data network.

One possible implementation for method 800 in FIG. 8 for an existing mobile data network, such as a 3G or 4G network, is shown as method 900 in FIG. 9. The requesting device sends a text message to the data chunk's device address (step 910). In response to the text message, the data chunk sends its data to the requesting device via one or more text messages (step 920). In one particular implementation, the data could be divided up into multiple chunks that can then be sent via sequential text messages, which could then be reassembled into the larger data portion by the device receiving the text messages. However, chopping the data into multiple portions that can be sent via text is not the only way to retrieve the data. With the ability to text photographs and other large files as attachments to a text message, the data chunk could simply send a text message with an attachment that includes the entire data portion of the data chunk. By making a data chunk addressable as a device, then sending a text message to the device to retrieve the data, the data chunks addressable as a device can be implemented within existing infrastructure in a mobile data network without any changes to hardware or software in the mobile data network.

Using existing support for text messages in an existing mobile data network is a low-cost method of implementing the data chunks that are addressable as devices, but may not provide the desired function or performance. As a result, an alternative implementation of a mobile data network 1000 shown in FIG. 10 supports data chunks that are addressable as devices. The user equipment 1010 preferably includes an app 1012 that allows communicating between the user equipment 1010 and the subscriber's data chunks that are addressable as devices. The user equipment 1010 communicates with a tower 320, which communicates with a basestation 330, which communicates with one or more network components 1020. Note that 1020 in FIG. 10 represents one or multiple network components. Thus, the features shown as part of the network components 1020 in FIG. 10 could exist in different components in the mobile data network 1000. For example, the subscriber database 1030 could exist in a first network component, the subscriber data mechanism 1040 could exist in a second network component, and the network storage 1080 could exist in a third network component. FIG. 10 is simplified to show different functions that could be implemented in different network components in a mobile data network.

The subscriber database 1030 resides in one of the network components 1020. The subscriber database 1030 includes subscriber information 1032 that specifies which physical devices 1034 are registered to a subscriber. Because the data chunk disclosed herein includes a device address, the physical devices 1034 preferably specify addresses of actual physical devices and additionally specify device addresses of data chunks owned by the subscriber that are addressable as devices.

A subscriber data mechanism 1040 resides in one of the network components 1020. Subscriber data mechanism 1040 preferably includes a subscriber data tracking mechanism 1050, a subscriber data transfer mechanism 1060, and a subscriber data management mechanism 1070. The subscriber data tracking mechanism 1050 tracks where subscriber data chunks are stored. The subscriber data transfer mechanism 1060 transfers data in the mobile data network when needed. The subscriber data management mechanism 1070 manages subscriber data in the mobile data network. Network storage 1080 also resides in one of the network components 1020. Network storage 1080 may include one or more data chunks 110.

Referring to FIG. 11, a method 1100 determines an unused device address for a subscriber (step 1110). The unused device address is written as the device address for a data chunk (step 1120). The device address for the data chunk is then written to the data tracking mechanism (step 1130), such as data tracking mechanism 1050 shown in FIG. 10. Method 1100 illustrates the steps in assigning a device address to a data chunk and registering the device address of the data chunk with the data tracking mechanism, which can then keep track of the data chunk. Because the data chunk is addressable as a device, the network infrastructure in the mobile data network that allows registering devices to a subscriber will inherently support registering data chunks to a subscriber.

A method 1200 in FIG. 12 illustrates how data is retrieved from a data chunk. A requesting device sends a request for data to the data chunk's device address (step 1210). In response to the request in step 1210, the data chunk sends its data portion to the requesting device (step 1220).

Referring to FIG. 13, data chunk status 130 from FIG. 1 is shown to include several fields, which may include a key, a description, an owner, whether the data chunk is copied or not, users who requested the data chunk, and a time to live (TTL). Of course, other fields not shown in FIG. 13 could be included in the data chunk status 130. The “key” field provides a unique identifier that supports querying the data chunk status 130. The “Description” field includes a description of the data. Note the description could include multiple fields. One description field could indicate type of data stored, such as text, e-mail, audio, video, graphic, application, etc. Another description field could indicate the relationship of the data chunk to a larger whole. For example, a description field could indicate that the data chunk is the sixth chunk of nine data chunks of audio data that make up a song. Another description field could indicate a title for the data chunk, such as the title of the song of which the data chunk is part. Another description field could indicate whether the data portion of the chunk is encrypted or not. Another description field could include validation values, such as checksums, that may be used for data transfer verification.

The “Owner” field specifies the subscriber or user that owns the data chunk. Note the owner of the data chunk need not necessarily be a subscriber to the mobile data network. For example, the mobile data network may have an agreement with a competitor network that allows the subscribers in the competitor network to store data chunks in the mobile data network. In this case, the owner could be a user of the competitor's network that is not a subscriber of the mobile data network. Specifying the owner of the data allows the data chunk to be more effectively managed.

The “Copied” field indicates whether the data is original or whether it was copied. Copied data is sometimes referred to as “forked data” because it exists in two places at once. An example of copied data is a web page downloaded from a web site. The data at the original website is not altered, and any data downloaded from a web site is necessarily a copy of the web page information residing on the server of the web page information. Knowing whether a data chunk is original or copied allows the data chunk to be more effectively managed.

The “Requested By” field indicates subscribers or users who have requested the data chunk. The “TTL” field can be used to indicate a time to live for the data chunk, such as an expiration date and time, a number of uses, or any other suitable way to specify when the data chunk should be retained or when the data chunk can be deleted, including any specific threshold, criteria, algorithm or heuristic.

A simple example will illustrate. Let's assume the data chunk is part of a web page that has been proactively downloaded to the mobile data network in anticipation of the subscriber needing the information. For example, let's assume the subscriber accesses the cnn.com website each morning around 7:00 AM, and is finished reading the news by 7:30 AM. The subscriber data management mechanism 1070 in FIG. 10 could proactively download the home page from cnn.com at 6:45 AM each morning so the information is readily available to the subscriber. Let's assume the home page is contained in a single data chunk. The data chunk status 130 shown in FIG. 13 for this example would include a key, a description of the date (web page at cnn.com), the owner of the data (subscriber X), that the data is copied data, that the data was requested by subscriber X, and has a TTL of 7:45 AM so the web page can be discarded after the normal time when the subscriber will no longer need it. In another example, a subscriber's data chunk may be made available to other subscribers or users. In this case, the TTL could be dynamically set according to the way the data is accessed. For example, if a data chunk that includes news is requested by other users, the TTL value could be increased, and the TTL could then decrease once there are no more accesses to the data chunk. This scenario dynamically adjusts the TTL for a data chunk to account for how the data chunk is accessed. Once the data chunk is no longer needed, the TTL will decrease to zero, and the data chunk could then be discarded.

The subscriber data tracking mechanism 1060 in FIG. 10 preferably keeps track of subscriber data. One suitable way for the subscriber data tracking mechanism 1060 to track subscriber data uses a subscriber data tracking table 1400 shown in FIG. 14. The tracking table 1400 includes multiple entries that each specifies owner, package, sub-package, and location as shown in FIG. 14. Thus, entry 1410 specifies that subscriber A owns the data chunk, that the data chunk is sub-package 0001 of package 1234, and the data is stored in location A1, which could represent a location on a physical device used by subscriber A. Entry 1420 specifies that subscriber A owns the data chunk, that the data chunk is sub-package 0002 of package 1234, and the data is stored in location A2. Entry 1430 specifies that subscriber A owns the data chunk, that the data chunk is sub-package 0003 of package 1234, and the data is stored in location B1. This could mean that data chunks owned by subscriber A could be stored on a physical device from subscriber B. Entry 1440 specifies that subscriber A owns the data chunk, that the data chunk is sub-package 0004 of package 1234, and the data is stored in location C5. This could mean that data chunks owned by subscriber A could be stored on a physical device from subscriber C. Thus, the first four entries 1410, 1420, 1430 and 1440 indicate that four chunks that make up package 1234 belong to subscriber A, with two of the chunks stored on physical devices belonging to A, one of the chunks stored on a physical device belonging to subscriber B, and one of the chunks stored on a physical device belonging to subscriber C. Similarly, entries 1450 and 1460 show two data chunks owned by subscriber B that are stored on B's and C's devices, and entries 1470, 1480 and 1490 show three data chunks owned by subscriber C that are stored in A's, B's and C's devices. The subscriber data tracking table 1400 is one suitable tool that could be used by the subscriber data tracking mechanism 1050 in FIG. 10 for keeping track of what data is stored where. In addition, the subscriber data tracking table 1400 could be written to each mobile device that includes any of the sub-packages listed in the tracking table. Thus, for the specific example in FIG. 14, the subscriber data tracking table 1400 could be copied to the mobile devices for owner A, owner B, and owner C. In addition, the data tracking table 1400 could reside in network storage in the mobile data network that is not part of any mobile device used by any subscriber of the mobile data network, such as network storage 1080 shown in FIG. 10.

FIG. 15 shows placement of data on different mobile devices as shown in the subscriber data tracking table 1400 shown in FIG. 14. Each mobile device includes storage for data chunks owned by the user (or subscriber) of the mobile device, and can additionally include storage for data chunks owned by other users of other mobile devices. Thus, subscriber A's mobile device 1010A includes storage 1510 for data chunks owned by subscriber A and storage 1520 for data chunks owned by others. In the nomenclature used in this example, the identifier preceding a period represents a package name while the identifier following the period represents a sub-package name. Thus, 1234.0001 1512 shown in subscriber A's mobile device 1010A denotes sub-package 0001 of package 1234. In this specific example, data chunks 1234.0001 1512 and 1234.0002 1514 are data chunks owned by subscriber A, while data chunk 3456.0003 1522 is owned by subscriber C, as shown in the subscriber data tracking table 1400 in FIG. 14. Similarly, subscriber B's mobile device 1010B includes storage 1530 for data chunks owned by subscriber B and storage 1540 for data chunks owned by others. Data chunk 2345.0001 1532 is owned by subscriber B, while data chunks 1234.0003 1542 and 3456.0002 1544 are owned by subscribers A and C, respectively. In like manner, subscriber C's mobile device 1010C includes storage 1550 for data chunks owned by subscriber C and storage 1560 for data chunks owned by others. Data chunk 3456.0001 1552 is owned by subscriber C, while data chunks 2345.0002 1562 and 1234.0004 1564 are owned by subscribers B and A, respectively. Note that the subscriber data tracking table 1400 shown in FIG. 14 is preferably written to each of the mobile devices 1010A, 1010B and 1010C shown in FIG. 15. In this manner each mobile device knows from its own table the location of all data chunks on all three devices.

FIG. 14 shows that Owner A owns a package 1234 that includes sub-packages 0001, 0002, 0003 and 0004 that correspond to data chunks A1, A2, B1 and C5 respectively. This data package 1234 is shown graphically in FIG. 16. Subscriber A's data 1610 includes package 1234 1620, which includes the four individual data chunks 1512, 1514, 1542 and 1564. Note that data chunks A1 1512 and A2 1514 are stored in mobile device 1010A for subscriber A, data chunk B1 1542 is stored in mobile device 1010B for subscriber B, and data chunk C5 1564 is stored in mobile device 1010C for subscriber C, as shown in FIG. 15. FIG. 16 represents that a file or package can be parsed into multiple data chunks, and different parts of the data chunks can be stored on different devices in the mobile data network. While the specific example in FIGS. 14-16 shows subscriber data distributed over three mobile devices, this is shown by way of example and is not limiting. Any suitable number of mobile devices can be used. In addition, any suitable number of different components in the mobile data network can also be used to hold subscriber data, such as network storage 1080 shown in FIG. 10. Thus, the disclosure and claims herein extend to storing subscriber data across any suitable number and type of mobile devices and across any suitable number and type of components in the mobile data network.

Note that the mobile devices can communicate with each other and with the subscriber data mechanism 1040 in the mobile data network using different networks. For example, for the embodiment in FIG. 15, subscriber A's mobile device 1010A could communicate with the mobile data network and with subscriber B's mobile device 1010B and subscriber C's mobile device 1010C via a Wi-Fi connection, while mobile devices 1010B and 1010C communicate with subscriber A's mobile device and with the mobile data network using a data path in the mobile data network. The disclosure and claims herein extend to communicating between mobile devices, between the mobile data network, and between other devices coupled to the mobile data network using any suitable network or combination of networks.

Any type of file may be parsed into multiple data chunks that can then be stored on multiple devices in a mobile data network. FIG. 17 shows that subscriber A's data 1710 could include audio files 1720, video files 1730, image files 1740, text files 1750, web pages 1760 and other files 1770. Audio files can be quite large, and parsing an audio file into multiple data chunks as disclosed herein would allow different data chunks that make up an audio file to be stored on different devices in the mobile data network. Video files 1730 can be even significantly larger than most audio files, so parsing the video files into multiple data chunks allows the different chunks to be stored on different devices in the mobile data network. Image files 1740 can also be quite large, and would benefit from being parsed into multiple data chunks as described herein. Text files 1750 could also be parsed into multiple data chunks. Web pages 1760 can include text, links, images, audio files, video files, etc. So one of the web pages 1760 could be parsed into multiple data chunks. For example, a web page could have one data chunk for text, other data chunks for graphics, other data chunks for video files, etc. Other files 1770 generically represents any other type of file not otherwise listed in FIG. 17, whether currently known or developed in the future.

Referring to FIG. 18, a method 1800 shows steps that can be performed to distribute data across different devices in a mobile data network. Method 1800 is preferably performed by the subscriber data mechanism 1040 shown in FIG. 10. In the alternative, method 1800 could be performed by an app 1012 on a mobile device 1010. Method 1800 begins when data needs to be distributed (step 1810). The data chunks to be distributed are identified (step 1820). The identification of data chunks in step 1820 can include identifying existing data chunks as well as generating new data chunks by parsing a file into multiple new data chunks. The data chunks can be part of the same file, or can be part of different files. The devices to which the identified data chunks will be distributed are then identified (step 1830). The data chunks are then distributed to the identified devices (step 1840). The location of the distributed data chunks is the written to a tracking table in the network (step 1850). The location of the distributed data chunks may also be written to each identified device that received data (step 1860). Method 1800 is then done.

Let's now review method 1800 to determine how it would work for the specific example shown in FIGS. 14-16. Referring to FIG. 14, we assume package 1234 owned by subscriber A is initially stored on the mobile device for subscriber A. In similar fashion, we assume package 2345 is initially stored on the mobile device for subscriber B, and package 3456 is initially stored on the mobile device for subscriber C. We assume that each mobile device for subscribers A, B and C runs an app 1012 as shown in FIG. 10 that allows the mobile devices to communicate with each other and share data with each other. We assume for this example that once all three apps on all three mobile devices communicate with each other, a determination is made that data needs to be distributed (step 1810). We assume for this example the packages 1234, 2345 and 3456 have not yet been parsed into sub-packages. So in response to determining that data needs to be distributed in step 1810, package 1234 is parsed into sub-packages 0001, 0002, 0003 and 0004; package 2345 is parsed into sub-packages 0001 and 0002; and package 3456 is parsed into sub-packages 0001, 0002 and 0003. For this example we assume each sub-package corresponds to a data chunk as described herein. Data chunks to be distributed are identified (step 1820). For the example in FIG. 14, we assume sub-packages 0003 and 0004 of package 1234 are identified to be distributed, sub-package 0002 of package 2345 is identified to be distributed, and sub-packages 0002 and 0003 of package 3456 are identified to be distributed in step 1820. The devices to which the identified data chunks will be distributed are then identified (step 1830). We assume for the example in FIG. 14 that decisions are made to distribute sub-package 0003 of package 1234 to subscriber B's mobile device, to distribute sub-package 0004 of package 1234 to subscriber C's mobile device, to distribute sub-package 0002 of package 2345 to subscriber C's mobile device, to distribute sub-package 0002 of package 3456 to subscriber B's mobile device, and to distribute sub-package 0003 of package 3456 to subscriber A's mobile device. The data chunks are then distributed to the identified devices (step 1840), with the result shown in FIG. 15. The location of the distributed data chunks is then written to a tracking table in the mobile data network (step 1850). For example, the subscriber data tracking table 1400 in FIG. 14 can be written to the network storage 1080 shown in FIG. 10. The location of the distributed data chunks is also written to each identified device that received one or more data chunks (step 1860). For example, the subscriber data tracking table 1400 in FIG. 14 can be written to each subscriber's mobile device. Thus, each mobile device 1010A, 1010B and 1010C could include the subscriber data tracking table 1400 shown in FIG. 14.

The specific example in FIGS. 14 and 15 show subscriber data chunks distributed to mobile devices of multiple subscribers in the mobile data network. Note, however, the data can be distributed to other types of devices as well, as illustrated in the embodiment shown in FIG. 19. Subscriber A's smart phone 1910 includes a memory 1920 that includes a subscriber data app 1922 and one or more of subscriber A's data chunks 1924. The subscriber data app 1922 can include a subscriber data mechanism similar to 1040 shown in FIG. 10 and discussed in detail above. In the alternative, the subscriber data app 1922 can include other features, as described with reference to FIG. 20 below. The subscriber data app 1922 thus provides the mechanisms for tracking, transferring and managing the subscriber's data chunks, and for communicating with subscriber data apps in other devices.

Subscriber B's smart phone 1912 includes a memory 1930 that includes a subscriber data app 1932 and one or more of subscriber A's data chunks 1934. Of course, the memory 1930 could also contain data chunks for Subscriber B or other subscribers, but only the data chunks for subscriber A are shown in FIG. 19 for the sake of simplifying the drawing and corresponding description. The subscriber data app 1932 could be the same as the subscriber data app 1922 in subscriber A's smart phone, or could be different. For example, if subscriber A's smart phone 1910 is an Android phone, and if subscriber B's smart phone 1912 is an iPhone, the subscriber data apps 1922 and 1932 will be different apps designed to run on their respective operating systems, but both will support the tracking, transfer and management of data chunks disclosed herein.

Basestation 1914 is a basestation that is in communication with Subscriber A's smart phone 1910. Note that basestation 1914 in FIG. 19 can represent different basestations in different locations in proximity to and in communication with subscriber A's smart phone 1910 as subscriber A's smart phone 1910 moves about. A basestation 1914 is similar in many respects to the prior art basestation 330 shown in FIGS. 3 and 10, with the added capability provided by the subscriber data app 1942 and the storage of subscriber data chunks, such as one or more subscriber A data chunks 1944. The subscriber data app 1942 could include the subscriber data mechanism 1040 shown in FIG. 10 and described in detail above. In the alternative, the subscriber data app 1942 can include other features, as described with reference to FIG. 20 below. The provider of the mobile data network could provide memory in basestations as shown at 1914 in FIG. 19 to extend the storage capability for subscriber data in the mobile data network.

Subscriber C's laptop 1916 includes a memory 1950 that includes a subscriber data app 1952 and one or more of subscriber A's data chunks 1954. Subscriber C's laptop 1916 could be coupled to the mobile data network via a wireless modem. In the alternative, subscriber C's laptop 1916 could be coupled to the mobile data network via a Wi-Fi connection. The subscriber data app 1952 could be the same as other subscriber data apps in the mobile data network, such as 1922, 1932, 1942 and 1962. In the alternative, the subscriber data app 1952 could be different than the other subscriber data apps, as long as it supports the tracking, transfer and management of data chunks disclosed herein. For example, an application for a laptop computer is typically different than an app for a smart phone.

A kiosk 1918 is shown in FIG. 19, which represents a device that could be owned by the mobile data network or could be owned by a third party subscriber to the mobile data network. Kiosk 1918 provides memory capacity for storing subscriber data chunks for a fee. The kiosk 1918 includes a memory 1960 that includes a subscriber data app 1962 and one or more of subscriber A's data chunks 1064. As with the other subscriber data apps, subscriber data app 1962 could be the same as one or more of the other subscriber data apps, or could be different, as long as it supports the tracking, transfer and management of data chunks disclosed herein. Because the kiosk charges a fee for use of its memory, and because subscriber A's data chunks 1064 are stored in the memory 1960 in the kiosk 1918, this implies subscriber A has previously authorized paying the required fee for storing subscriber A's data chunks 1064 in the memory 1960 of kiosk 1918. Of course, the disclosure and claims herein extend to storing a subscriber's data in a device such as a kiosk that does not require payment of a fee.

The types of devices shown in FIG. 19 are not limiting, but are shown by way of example. The disclosure and claims herein expressly extend to any suitable device, whether a network component in the mobile data network, a subscriber device, or a device coupled to the mobile data network that is provided by a third party.

FIG. 20 shows one suitable embodiment for the subscriber data app 1922 shown in FIG. 19. The same or similar configuration could apply to all of the subscriber data apps 1922, 1932, 1942, 1952 and 1962 shown in FIG. 19. Subscriber data app 1922 includes a subscriber data mechanism 2040. The subscriber data mechanism 2040 includes a subscriber data tracking mechanism 2050, a subscriber data transfer mechanism 2060, a subscriber data management mechanism 2070, a subscriber history mechanism 2080, and a subscriber data prediction mechanism 2090. The mechanisms 2050, 2060 and 2070 could have similar functions to the corresponding mechanisms 1050, 1060 and 1070 shown in FIG. 10 and described above. Of course, mechanisms 2050, 2060 and 2070 could have different or additional functions as well. The subscriber history mechanism 2080 monitors data chunks used by the subscriber, and writes the data chunks used by the subscriber to a historical log 2082. The subscriber data prediction mechanism 2090 analyzes the historical log 2082 to determine trends in the usage of the data chunks by the subscriber. Based on an analysis of the historical log 2082, the subscriber data prediction mechanism 2090 can predict data, a location, and a time when the subscriber may likely need to access the data in the future. The predicted data 2092, predicted location 2094, and predicted time 2096 are shown in FIG. 20. Based on the predicted data 2092, predicted location 2094, and predicted time 2096, the subscriber data prediction mechanism 2090 can proactively move subscriber data between devices in the mobile data network as needed to provide the best performance for the subscriber. In particular, the subscriber data prediction mechanism 2090 moves the predicted data 2092 to the predicted location 2094 to be available at the predicted time 2096, wherein the predicted data comprises at least one of the subscriber's data chunks.

Referring to FIG. 21, a method 2100 is preferably performed by the subscriber history mechanism 2080 shown in FIG. 20. The data chunks used by a subscriber are monitored (step 2110). The data chunks used by the subscriber are written to the historical log (step 2120). Note the monitoring of data chunks in step 2110 and logging of the monitored data in step 2120 can be performed for one subscriber at a time, or could be performed for multiple subscribers simultaneously. In addition, the historical log could contain historical information for a single subscriber, or could contain historical information for multiple subscribers. Method 2100 is then done.

Referring to FIG. 22, a method 2200 is preferably performed by the subscriber data prediction mechanism 2090. The historical log for a subscriber is read (step 2210). The data in the historical log is analyzed to determine trends in the subscriber's data usage to determine predicted data, predicted location, and predicted time (step 2220). The predicted data is then moved to the predicted location to be available at the predicted time (step 2230). In the most preferred implementation, the data is moved before the predicted time so the data is available in the predicted location at the predicted time. Method 2200 is then done.

A simple example will illustrate the function of the subscriber data prediction mechanism 2090 shown in FIG. 20. Let's assume a salesperson has to regularly traverse a large remote region to meet with customers. The salesperson uses mass transit to go from region to region and during the transition she wants to look at information about the customer she is visiting next. Let's assume each time the salesperson makes this trip, she starts by first visiting customers A and B in location 1, followed by visiting customers C and D in location 2. The subscriber data prediction mechanism 2080 would identify this pattern from the historical log 2082 and ensure that the data for the customer at the next location is available at the previous location. Thus, as the salesperson is traveling to location 1 near customers A and B, the subscriber data prediction mechanism 2090 could download data relating to customers A, B, C and D to a kiosk at location 1. When the salesperson arrives in location 1, the data for customers A, B, C and D can be downloaded from the kiosk to the salesperson's mobile device. The salesperson could change the date relating to customers A and B, which could result in the changed data being stored to the kiosk at location 1, which can then send the changed data back to the salesperson's company database. When the salesperson is done at location 1 and is traveling to location 2, the data for customers C and D will be available for the salesperson to review on the salesperson's mobile device in transit between location 1 and location 2. As the salesperson travels from location 1 to location 2, the subscriber data prediction mechanism 2090 could delete the data for customers A and B from the subscriber's mobile device.

In another example, the subscriber data prediction mechanism 2090 can determine what information the subscriber may need at a point along a subscriber's path when the path and points are predefined, such as stops on a train, even when the subscriber has never ridden the train before. In this case the subscriber data prediction mechanism 2090 would look at the fact that the user is traveling by train, which has a constrained path with defined schedule information. Using this information the subscriber data prediction mechanism 2090 can move required data to the different stops such that the appropriate pieces of data will be at each stop when the subscriber arrives. For example, let's assume a subscriber is reading a large document on their phone as they ride the train. They are reading at a rate of 3 pages per minute. Let's further assume the train will stop at station A, then travel for 10 minutes to station B. When the train is stopped at station A, the subscriber data prediction mechanism 2090 can determine the train will arrive at station B in 10 minutes, so the subscriber will need 30 more pages of data available at station A. As a result, the 30 pages of data is moved to a location at station A and loaded onto the subscriber's phone when the subscriber arrives at station A. In addition, the subscriber data prediction mechanism 2090 can also use information about the other passengers and load the data needed by the subscriber onto devices of passengers getting on the train. When the subscriber data prediction mechanism 2090 detects a passenger that has data that was previously downloaded on their device is getting off the train, the data could be moved to the device of another passenger that is still on the train.

In one particular embodiment, some locations that store data could do so for a fee. For example, the kiosk 1918 in FIG. 19 and the kiosk described in the example above could charge a fee for the subscriber to be able to access the subscriber's data. Referring to FIG. 23, a method 2300 determines whether or not to move a subscriber's data chunks to a better location. When a better location for a fee is not available (step 2310=NO), method 2300 is done. When a better location is available for a fee (step 2310=YES), the subscriber is prompted to authorize the fee for the better location (step 2320). When the subscriber does not authorize the fee (step 2330=NO), method 2300 is done. When the subscriber authorizes the fee (step 2330=YES), the better location is then available for the storage of the subscriber's data (step 2340). Method 2300 is then done. Method 2300 shows how a subscriber can decide to pay to have data moved to a better location that improves the performance for the subscriber. Thus, in the example above regarding a passenger on a train, the train could include mobile Internet technology that could serve the functions of a mobile kiosk.

FIG. 24 shows an embodiment for sharing data among subscriber devices. Subscriber A's smart phone 2410 includes a memory 2420 that includes a subscriber data app 2422. Similarly, subscriber B's smart phone 2412 has a memory 2430 that includes a subscriber data app 2432; subscriber C's smart phone 2416 has a memory 2450 that includes a subscriber data app 2452; subscriber D's smart phone 2418 has a memory 2460 that includes a subscriber data app 2462; and basestation 2414 has a memory 2440 that includes a subscriber data app 2442. The basestation 2414 is preferably a basestation in the mobile data network. In the embodiment shown in FIG. 24, the subscriber's smart phones communicate with the basestation 2414 using standard cell phone signals and communication protocols, as shown by the solid lines with arrows in FIG. 24. In addition, the subscriber's smart phones may communicate with each other via Wi-Fi, Bluetooth, or any other suitable network, as shown by way of example by the dotted lines with arrows in FIG. 24. For the sake of simplicity, not all possible connections are shown in FIG. 24. For example, while subscriber B's smart phone 2412 is shown connected with dotted lines to subscriber A's smart phone 2410 and subscriber C's smart phone 2416, it could also be connected to subscriber D's smart phone 2418, although such a connection is not explicitly shown in FIG. 24. The disclosure and claims herein expressly extend to any suitable network or communication mechanism between subscriber devices and between subscriber devices and the mobile data network.

The types of devices shown in FIG. 24 are not limiting, but are shown by way of example. The disclosure and claims herein expressly extend to any suitable device, whether a network component in the mobile data network, a subscriber device, or a device coupled to the mobile data network that is provided by a third party.

FIG. 25 shows one suitable embodiment for the subscriber data app 2422 shown in FIG. 24. The same or similar configuration could apply to all of the subscriber data apps 2422, 2432, 2442, 2452 and 2462 shown in FIG. 24. Subscriber data app 2422 includes a subscriber data mechanism 2540. The subscriber data mechanism 2540 includes a subscriber data tracking mechanism 2050, a subscriber data transfer mechanism 2060, a subscriber data management mechanism 2070, a subscriber history mechanism 2080, and a subscriber data prediction mechanism 2090, as shown in FIG. 20 and discussed in more detail above. The mechanisms 2050, 2060 and 2070 could have similar functions to the corresponding mechanisms 1050, 1060 and 1070 shown in FIG. 10 and described above. Of course, mechanisms 2050, 2060 and 2070 could have different or additional functions as well. Similarly, the mechanisms 2080 and 2090 could have similar functions to the corresponding mechanisms shown in FIG. 20 and described above. The subscriber data mechanism 2540 additionally includes a device discovery mechanism 2510 and a query mechanism 2520. The device discovery mechanism 2510 allows a subscriber's device to determine which devices are related to it based on some predefined relation criteria, and to establish an ad-hoc network with related devices. This can be done by the subscriber device querying the mobile data network, querying neighboring devices, or any suitable combination of the two. The query mechanism 2520 allows the subscriber data mechanism 2540 to determine whether data requested by a subscriber is present on a device, and if so, to have the data returned by the device instead of requesting the data from the mobile data network. Details and examples follow.

Referring to FIG. 26, a method 2600 is preferably performed by the device discovery mechanism 2510 in FIG. 25. Related devices are discovered (step 2610). An ad-hoc network is then established with any discovered related devices (step 2620). Method 2600 is then done. Devices can be related by any suitable relation criteria. Examples of two relation criteria are shown in FIG. 27 to include common location 2710 and common activity 2720. Common location 2710 can specify any suitable location criteria, including devices on the same Wi-Fi network, devices connected to the same basestation, and devices connected to a set of basestations that are in a defined geographical region. Thus, subscriber devices running the subscriber data app 2422 shown in FIG. 25 can be related when the subscriber devices are on the same Wi-Fi network or are connected to the same basestation. A simple example will illustrate. Let's assume a subscriber walks into a concert venue that has a Wi-Fi network, and the subscriber's device connects to the Wi-Fi network. The device discovery mechanism 2510 can send out inquiries to discover devices via the mobile data network or the Wi-Fi network. Let's assume there are ten other subscribers at the concert venue that are running subscriber data apps such as 2422 shown in FIG. 24. The ten devices running these apps respond to the inquiry to discover devices, which can result in an ad-hoc network being formed with the subscriber device and the ten other devices that responded to the discovery inquiry. In this manner, ad-hoc networks of subscriber devices can be established to share data between the subscriber devices, as described further below.

The simple example above illustrates the establishment of an ad-hoc network with devices in a common location 2710, namely, in the concert venue. In a different example, the common location 2710 could be defined by all devices connected to a common basestation. Thus, devices that are not in direct physical proximity could be related because they are connected to a common basestation. For example, let's assume a college is having sports rallies at different locations on campus, and the campus is served by a single basestation. The devices connected to the same basestation could be related by common location, and an ad-hoc network could be established among devices connected to the same basestation, even when the devices are not in close physical proximity to each other.

In another example, common location 2710 could be defined as any device within a defined geographical region covered by multiple basestations. Thus, let's assume a parade in a large city spans a route that is covered by three different basestations. The devices related by being connected to any of these three different basestations could be connected in an ad-hoc network.

The second relation criteria shown in FIG. 27 is common activity 2720. This allows subscriber devices at different geographic locations to be related to each other based on a common activity. For example, let's assume the University of Notre Dame is having a football rally on its main campus, and faithful Irish fans are participating in the rally at six different locations across the United States. The fact these fans are participating in the same football rally could be the common activity 2720 that allows the devices of these fans to be related and thus in an ad-hoc network, even though they are not in physical proximity to each other.

Once related devices are connected in an ad-hoc network as shown in step 2620 in FIG. 26, the devices can share data. Referring to FIG. 28, method 2800 begins when a subscriber's device needs to perform a data query for requested data (step 2810). The devices in the ad-hoc network are queried for the requested data (step 2820). When the data is available on one of the devices in the ad-hoc network (step 2830=YES), the data is returned from the device to the device that queried for the requested data (step 2840). When the data is not available on any of the devices in the ad-hoc network (step 2830=NO), the data query is submitted to the mobile data network (step 2850) and the data corresponding to the query is returned to the subscriber's device from the mobile data network (step 2860). Method 2800 is then done. Method 2800 illustrates that when data requested by a subscriber's device in an ad-hoc network is available from another device in the ad-hoc network, the data can be returned directly in the ad-hoc network without the need for querying the mobile data network for the data. For example, in the concert example discussed above, let's assume that during an opening performance by Band A, a first subscriber accesses a web page for Band B, which is the next group to perform. Let's further assume a second subscriber then requests the same web page for Band B that the first subscriber already downloaded to the first subscriber's mobile device. In this scenario, the query for the web page for Band B by the second subscriber device can be routed to the first subscriber device, which then returns the web page for Band B to the second subscriber device without the second subscriber device having to access the web page via the mobile data network. The examples above illustrate the dynamic formation of ad-hoc networks, and data transfer directly between devices in an ad-hoc network to improve performance by not querying the mobile data network each time a subscriber device requests data. Note the ad-hoc network can be very dynamic, adding subscriber devices as they are discovered and dropping subscriber devices when needed, such as when a subscriber leaves a common location or no longer is participating in a common activity.

Referring to FIG. 29, a method 2900 is preferably performed by a subscriber data app 2442 running on a basestation as shown in FIG. 24. Subscriber data app 2442 is preferably similar to subscriber data app 2422 shown in FIG. 25. Basestations that have similar queries are detected (step 2910). An ad-hoc grouping of basestations is then created based on the similar queries (step 2920). Data can then be replicated to the ad-hoc grouping of basestations to satisfy similar queries (step 2930). Method 2900 could be used for the example given above for the rally for Notre Dame football. Let's assume during the rally a video clip is shown. Let's further assume the showing of the video clip prompts several subscribers at different locations to make similar queries to access the same data, such as a related video on a website. When the different basestations at the different locations detect similar queries in step 2910, an ad-hoc grouping of the basestations can be created in step 2920. Based on the ad-hoc grouping of basestations, data in one basestation can be replicated to the other basestations to satisfy similar queries from other subscriber devices. Thus, the first request for a video will have to traverse the mobile data network to retrieve the video from the Internet. Once the basestations detect other requests for the video, the video file could be replicated to each basestation in the ad-hoc grouping of basestations, which will allow each basestation to return the video to any devices connected to it that request the video without having to request the video from the Internet coupled to the mobile data network. For data such as web pages, the data chunk owned by the subscriber is a copy, which means the data chunk could be discarded when the web page is no longer needed.

In one suitable embodiment, the basestations could load-balance data based on each basestation's connection to the Internet, connection to each other basestation, and data within its local network. For example, if currently one basestation has a lot of extra bandwidth to the Internet, it could be used as a query point for other basestations. In another embodiment, if a basestation contains possible information needed by other basestations, it will broadcast and let other basestations decide whether to obtain from needed data from that basestation, locally, via the Internet, or some combination of these.

Data chunks are data structures that do not include any hardware. Making data chunks addressable as devices makes the data chunks appear as traditional physical devices that include hardware. In this manner data chunks can be addressed as if they are physical devices in the mobile data network.

A mobile data network supports making subscriber data addressable as devices in a mobile data network. Each data chunk is assigned a device address in the mobile data network. The data chunk can then be addressed as a device in the mobile data network. Data chunks corresponding to a subscriber are distributed across multiple devices in the mobile data network, which may include subscriber devices, network components in the mobile data network, and specialized devices provided by storage providers. The mobile data network is queried to determine related devices. An ad-hoc network of the related devices is formed. A data query by one of the related devices is sent to the related devices in the ad-hoc network to determine whether the data query can be satisfied by one of the related devices. If not, the data query is sent via normal channels in the mobile data network.

One skilled in the art will appreciate that many variations are possible within the scope of the claims. Thus, while the disclosure is particularly shown and described above, it will be understood by those skilled in the art that these and other changes in form and details may be made therein without departing from the spirit and scope of the claims. 

The invention claimed is:
 1. A mobile data network comprising: an antenna that communicates with user equipment; at least one basestation coupled to the antenna that communicates with the user equipment via the antenna; a plurality of data chunks residing in the mobile data network; a subscriber data mechanism residing in a first device coupled to the mobile data network that performs the steps of: determining a plurality of related devices that includes the first device according to at least one predefined relation criterion; establishing an ad-hoc network of the plurality of related devices; the first device submitting a query requesting data from other of the plurality of related devices in the ad-hoc network; when the requested data is available in one of the other of the plurality of related devices, the one other related device returning the requested data to the subscriber data mechanism; and when the requested data is not available in any of the related devices, submitting the query to the mobile data network, and in response, the mobile data network returns the requested data to the subscriber data mechanism.
 2. The mobile data network of claim 1 wherein the identified plurality of devices comprises a plurality of mobile devices used by different subscribers of the mobile data network.
 3. The mobile data network of claim 1 wherein the identified plurality of devices comprises network storage in the mobile data network that is not part of any mobile device used by any subscriber of the mobile data network.
 4. The mobile data network of claim 1 wherein the identified plurality of devices comprises storage coupled to the mobile data network that is not part of any mobile device used by any subscriber of the mobile data network and that is not part of any network component in the mobile data network.
 5. The mobile data network of claim 1 wherein the at least one relation criterion comprises devices in a common location.
 6. The mobile data network of claim 5 wherein each of the plurality of related devices communicates with a common basestation.
 7. The mobile data network of claim 5 wherein each of the plurality of related devices communicates with a set of basestations in a defined geographical region.
 8. The mobile data network of claim 1 wherein the at least one relation criterion comprises devices engaged in a common activity.
 9. The mobile data network of claim 1 wherein each data chunk further comprises a status that comprises a key and a description of the data chunk. 